Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 22, 2024

This PR contains the following updates:

Package Change Age Confidence
Microsoft.Extensions.DependencyInjection (source) 8.0.1 -> 9.0.10 age confidence
Microsoft.Extensions.Logging (source) 8.0.1 -> 9.0.10 age confidence
Microsoft.Extensions.Logging.Debug (source) 8.0.1 -> 9.0.10 age confidence

Release Notes

dotnet/dotnet (Microsoft.Extensions.DependencyInjection)

v9.0.7: .NET 9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.6: .NET 9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.5: .NET 9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.4: .NET 9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.3: .NET 9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.2: .NET 9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.1: .NET 9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

v9.0.0: .NET 9.0.0

You can build .NET 9.0 from the repository by cloning the release tag v9.0.0 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from b84e088 to 01629df Compare January 24, 2025 21:38
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 01629df to ec6535d Compare February 21, 2025 19:08
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from ec6535d to 1a2220e Compare March 21, 2025 19:38
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 1a2220e to f8ea805 Compare April 18, 2025 19:51
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from f8ea805 to 86ffd10 Compare May 23, 2025 22:25
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from d5654a3 to ab10e52 Compare June 20, 2025 20:00
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from ab10e52 to c79a96f Compare July 18, 2025 18:33
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch 2 times, most recently from ebdfa2d to fc80292 Compare August 15, 2025 02:29
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from fc80292 to 88acbcc Compare September 19, 2025 14:47
@renovate renovate bot force-pushed the renovate/major-dotnet-monorepo branch from 88acbcc to 6b67fe2 Compare October 24, 2025 20:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant